Clarify how AnimationTrack:Stop() with a fadeTime of 0 affects Motor6Ds#1036
Merged
IgnisRBX merged 3 commits intoRoblox:mainfrom Feb 26, 2025
Merged
Clarify how AnimationTrack:Stop() with a fadeTime of 0 affects Motor6Ds#1036IgnisRBX merged 3 commits intoRoblox:mainfrom
IgnisRBX merged 3 commits intoRoblox:mainfrom
Conversation
There was a problem hiding this comment.
Hi @Starveldt, thanks so much for helping improve the Roblox creator documentation! Our technical writing team will review your pull request soon. In the meantime, please ensure you've read through the README.md, contribution guidelines, and style recommendations.
IgnisRBX
reviewed
Feb 26, 2025
IgnisRBX
approved these changes
Feb 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
When calling
AnimationTrack:Stop()with a fadeTime of 0, poses do not freeze under all circumstances. It happens due to theMaxVelocityof Motor6Ds in the rig being zero, meaning they cannot return back to their desired angle (since they inherit Motors).I believe the misconception in the passage I edited was due to the default StarterCharacter rigs having the MaxVelocity of all joints set to zero rather than something like tau (which should be optimal, given MaxVelocity is in radians). I've also tested this below.
Rig with MaxVelocity set to 0 for all Motor6Ds, calling

AnimationTrack:Stop(0):Rig with MaxVelocity set to tau for all Motor6Ds, calling

AnimationTrack:Stop(0):Bones are not affected by this issue since they do not inherit Motor.
Checks
By submitting your pull request for review, you agree to the following: